-
Notifications
You must be signed in to change notification settings - Fork 74k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[INTEL MKL] Fix proxy info during docker builds #29560
Conversation
Hi @penpornk any feedback on this? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for the delay!
I'm not sure why either, but adding these doesn't hurt. Thank you!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On second thought, please add a comment (in the docker file) why they are added. For future reference.
Thanks @penpornk |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the changes! I was referring to why the uppercase letter ones need to be added. But additional info is great too! Sorry for being unclear.
TF_DOCKER_BUILD_ARGS+=("--build-arg HTTP_PROXY=${http_proxy}") | ||
TF_DOCKER_BUILD_ARGS+=("--build-arg SOCKS_PROXY=${socks_proxy}") | ||
TF_DOCKER_BUILD_ARGS+=("--build-arg NO_PROXY=${no_proxy}") | ||
TF_DOCKER_BUILD_ARGS+=("--build-arg HTTP_PROXY=${HTTP_PROXY}") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add a comment explaining that we need the uppercase versions because the lowercase ones don't cover all the case (or something).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @penpornk to best of my knowledge I added a comment to describe why we need both set of proxies 🙂
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you very much, @ashahba! :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for your patience!
TF_DOCKER_BUILD_ARGS+=("--build-arg HTTP_PROXY=${http_proxy}") | ||
TF_DOCKER_BUILD_ARGS+=("--build-arg SOCKS_PROXY=${socks_proxy}") | ||
TF_DOCKER_BUILD_ARGS+=("--build-arg NO_PROXY=${no_proxy}") | ||
TF_DOCKER_BUILD_ARGS+=("--build-arg HTTP_PROXY=${HTTP_PROXY}") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you very much, @ashahba! :)
PiperOrigin-RevId: 253897496
This was causing
swift
package downloads to fail because for some reasonHTTP_PROXY
andHTTPS_PROXY
values were empty.